From: squirrel@echelon.alias.net (The Tech Lion)
Subject: FZ BIBLE - LEVEL 3 COURSEPACK [4/7]
Date: 14 Nov 1999 00:00:00 GMT
Message-ID: <cb3c96fe638a313800b9dd4675b8bf20@anonymous.poster>
Sender: Secret Squirrel <squirrel@echelon.alias.net>
Organization: FreeZone Bible Association
Mail-To-News-Contact: postmaster@nym.alias.net
Comments: Please report problems with this automated remailing service to <squirrel-admin@echelon.alias.net>. The message sender's identity is unknown, unlogged, and not replyable.
Newsgroups: alt.religion.scientology,alt.clearing.technology

FREEZONE BIBLE ASSOCIATION TECH POST

ACADEMY LEVEL III COURSEPACK: Part 4 of 7

***************************************

Continuing our quest to spread the Tech on the internet,
we bring you the Academy Level 3 coursepack from the late
1980s, in 7 parts.

The full table of contents is in Part 1 only.

To see the proper formatting, use a fixed-pitch font such as
Courier to view this file.

Looking forward to a Tech-filled Millenium,

-The Tech Lion 

********************

STATEMENT OF PURPOSE 

Our purpose is to promote religious freedom and the Scientology
Religion by spreading the Scientology Tech across the internet.

The Cof$ abusively suppresses the practice and use of
Scientology Tech by FreeZone Scientologists.  It misuses the
copyright laws as part of its suppression of religious freedom.

They think that all freezoners are "squirrels" who should be
stamped out as heretics.  By their standards, all Christians, 
Moslems, Mormons, and even non-Hassidic Jews would be considered
to be squirrels of the Jewish Religion.

The writings of LRH form our Old Testament just as the writings
of Judaism form the Old Testament of Christianity.

We might not be good and obedient Scientologists according
to the definitions of the Cof$ whom we are in protest against.

But even though the Christians are not good and obedient Jews,
the rules of religious freedom allow them to have their old 
testament regardless of any Jewish opinion.  

We ask for the same rights, namely to practice our religion
as we see fit and to have access to our holy scriptures
without fear of the Cof$ copyright terrorists.

We ask for others to help in our fight.  Even if you do
not believe in Scientology or the Scientology Tech, we hope
that you do believe in religious freedom and will choose
to aid us for that reason.

Thank You,

The FZ Bible Association

************************

PART 4

11. HCOB   27 May  1963       Cause of ARC Breaks

12. HCOB   19 Aug. 1963       How to Do an ARC Break Assessment

13. HCOB    7 Sept 1964 II    PTPS, Overts and ARC Breaks

14. HCOB   29 Mar. 1965       ARC Breaks

15. HCOB    4 Apr. 1965       ARC Breaks and Missed Withholds


******************************************************************

11. HCOB   27 May  1963       Cause of ARC Breaks


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

       HCO BULLETIN OF 27 MAY 1963

CenOCon
Franchise

                ALL AUDITING
STAR-RATING HCO BULLETIN FOR ACADEMIES AND SHSBC


            CAUSE OF ARC BREAKS


LUCKY IS THE PC WHOSE AUDITOR HAS UNDERSTOOD THIS HCO BULLETIN. 
AND LUCKY IS THE AUDITOR, MAY HIS OWN CASE RUN WELL.

I have just narrowed the reason for ARC breaks in auditing 
actions down to only one source.

  RULE: ALL ARC BREAKS ARE CAUSED BY BYPASSED CHARGE.

  RULE: TO TURN OFF AN ARC BREAK FIND AND INDICATE THE CORRECT
        BYPASSED CHARGE.

Charge can be bypassed by

1. Going later than basic on any chain without further search for 
basic.

Example: Looking for the pc's first automobile accident, finding 
the fifth instead and trying to run the fifth accident as the 
first accident, which it isn't. The bypassed charge here is the 
first accident and all succeeding accidents up to the one 
selected by the auditor as the first one or the one to run. To a 
greater or lesser degree depending on the amount the earlier 
material was restimulated, the pc will then ARC break (or feel 
low or in "low morale"). One can run a later incident on a chain 
briefly but only to unburden earlier incidents, and the pc must 
know this.

2. Unknowingly ignoring the possibility of a more basic or 
earlier incident of the same nature as that being run after the 
pc has been restimulated on it. Or bluntly refusing to admit the 
existence of or let the pc "at" an earlier incident.

3. Cleanly missing a GPM, as one between two goals run 
consecutively in the belief they are consecutive.

4. Missing an earlier GPM and settling down to the assertion 
there are no earlier ones.

5. Cleanly missing one or more RIs, not even calling them.

6. Failing to discharge an RI and going on past it.

7. Accidentally missing a whole block of RIs, as in resuming 
session and not noticing pc has skipped (commoner than you'd 
think).

8. Accepting a wrong goal, missing the right one similarly 
worded.

9. Accepting a wrong RI, not getting the plot RI to fire.

10. Misinterpreting or not understanding data given to you by the 
pc and/or acting on wrong data.

11. Misinforming the pc as to what has or has not fired and 
discharged.

12. Locating the wrong bypassed charge and saying it is the 
source of the ARC break.

13. Failing to follow the cycle of communication in auditing.

These and any other way charge can be restimulated and left prior 
to where the auditor is working can cause an ARC break.

Charge left after (later) (nearer PT) than where the auditor is 
working hardly ever causes an ARC break.

The burden of skilled auditing, then, is to get RIs (and GPMs and 
incidents) discharged as close to basic (first incident) as 
possible. And always be prowling for something earlier.

In contradiction of this is that any GPM fairly well discharged 
by RRs unburdens the case, ARC break or no ARC breaks. And any 
incident partially discharged lets one go earlier.

The pc never knows why the ARC break. He may think he does and 
disclaim about it. But the moment the actual reason is spotted 
(the real missed area) the ARC break ceases.

If you know you've missed a goal or RI, just saying so prevents 
any ARC break.

An ARC breaky pc can always be told what has been missed and will 
almost always settle down at once.

Example: Pc refuses to come to session. Auditor on telephone says 
there's a more basic incident or RI or GPM. Pc comes to session.

The auditor who is most likely to develop ARC breaks in the pc 
will have greater difficulty putting this HCO Bulletin into 
practice. Perhaps I can help this. Such an auditor Q-and-As by 
action responses, not acknowledgments after understanding. Action 
can be on an automaticity in the session. So this HCO Bulletin 
may erroneously be interpreted to mean "If the pc ARC breaks DO 
something earlier."

If this were true, then the only thing left to run would be 
basic-basic -- without the pc being unburdened enough to have any 
reality on it.

A drill (and many drills can be compiled on this) would be to 
have a lineal picture of a time track. The coach indicates a late 
incident on it with a pointer and says, "Pc ARC break." The 
student must give a competent and informative statement that 
indicates the earlier charge without pointing (since you can't 
point inside the reactive bank of a pc with a pointer). Drawn 
time tracks showing a GPM, a series of engrams along free track, 
a series of GPMs, all plotted against time, would serve the 
purpose of the drill and give the student graphic ARC break 
experience.

The trick is TO FIND AND INDICATE the RIGHT bypassed charge to 
the pc and to handle it when possible but never fail to indicate 
it.

It is not DO that heals the ARC break but pointing toward the 
correct charge.

  RULE: FINDING AND INDICATING AN INCORRECT BYPASSED CHARGE WILL
        NOT TURN OFF AN ARC BREAK.

An automaticity (as covered later in this HCO Bulletin) is 
rendered discharged by indicating the area of charge only.

This is an elementary example: Pc says, "I suppressed that." 
Auditor says, "On this incident has anything been suppressed?" Pc 
ARC breaks. Auditor indicates charge by saying, "I'm sorry. A 
moment ago I didn't acknowledge your suppression." ARC break 
ceases. Why? Because the source of its charge that triggered an 
automaticity of above the pc's tone, was itself discharged by 
being indicated.

Example: Auditor asks for a Joburg overt. Pc gives it. Auditor 
consults meter at once asking question again, which is protested 
giving a new read. Pc ARC breaks. Auditor says, "I did not 
acknowledge the overt you gave me. I acknowledge it." ARC break 
ceases.

Example: Auditor asks for RI No. 173 on First Series Line Plot. 
Pc ARC breaks, giving various reasons why, such as auditor's 
personality. Auditor asks meter, "Have I missed an item on you?" 
Gets read. Says to pc, "I've missed an item." ARC break ceases. 
Whether the missing item is looked for or not is immaterial to 
this HCO Bulletin which concerns handling ARC breaks.

If an auditor always does in response to an ARC break, such as 
instantly looking for specific earlier items, that auditor has 
missed the point of this HCO Bulletin and will just pile up more 
ARC breaks, not heal them.

Don't be driven by ARC breaks into unwise actions, as all you 
have to do is find and indicate the missing charge that was 
bypassed. That is what takes care of an ARC break, not taking the 
pc's orders.

If the ARC break does not cease, the wrong bypassed charge has 
been indicated.

The sweetest running pc in the world can be turned into a tiger 
by an auditor who always Q-and-As, never indicates charge and 
goes on with the session plan.

Some Q and As would be a source of laughter if not so deadly.

Here is a Q-and-A artist at work (and an ARC breaky pc will soon 
develop) (and this auditor will soon cease to audit because it's 
"so unpleasant").

Example: Auditor: "Have you ever shot anyone?" Pc: "Yes, I shot a 
dog." Auditor: "What about a dog?" Pc: "It was my mother's." 
Auditor: "What about your mother?" Pc: "I hated her." Auditor: 
"What about hating people?" Pc: "I think I'm aberrated." Auditor: 
"Have you worried about being aberrated?" Pc: @!!*?!!.

Why did the pc ARC break? Because the charge has never been 
permitted to come off shooting a dog, his mother, hating people, 
and being aberrated and that's enough bypassed charge to blow a 
house apart.

This pc will become, as this keeps up, unauditable by reason of 
charge missed in sessions and his resulting session 
dramatizations as overts.

Find and indicate the actual charge bypassed. Sometimes you can't 
miss it, it has just happened. Sometimes you need a simple meter 
question since what you are doing is obvious. Sometimes you need 
a dress parade assessment from a list. But however you get it, 
find out the exact bypassed charge and then INDICATE IT TO THE 
PC.

The violence of an ARC break makes it seem incredible that a 
simple statement will vanquish it, but it will. You don't have to 
run another earlier engram to cure an ARC break. You merely have 
to say it is there-and if it is the bypassed charge, that ARC 
break will vanish.

Example: Pc: "I think there's an incident earlier that turned off 
my emotion." Auditor: "We'd better run this one again." Pc ARC 
breaks. Auditor: (Consults meter) "Is there an earlier incident 
that turns off emotion?" (Gets read) "Say, what you just said is 
correct. Thank you. There is an earlier incident that turns off 
emotion. Thank you. Now let's run this one a few more times." 
Pc's ARC break ends at once.

Don't go around shivering in terror of ARC breaks. That's like 
the modern systems of government which tear up their whole 
constitution and honor just because some hired demonstrators 
howl. Soon they won't be a government at all. They bend to every 
ARC break.

ARC breaks are inevitable. They will happen. The crime is not, to 
have a pc ARC break. The crime is, not to be able to handle one 
fast when it happens. You must be able to handle an ARC break 
since they are inevitable. Which means you must know the 
mechanism of one as given here, how to find bypassed charge and 
how to smoothly indicate it.

To leave a pc in an ARC break more than two or three minutes, is 
just inept.

And be well-drilled enough that your own responding rancor and 
surprise doesn't take charge. And you'll have pleasant auditing.

           ARC BREAK PROCESSES

We had several ARC break processes. These were repetitive 
processes.

The most effective ARC break process is locating and indicating 
the bypassed charge. That really cures ARC breaks.

A repetitive command ARC break process based on this discovery I 
just made would possibly be "What communication was not 
received?"

Expanding this we get a new ARC Straightwire:

  "What attitude was not received?"

  "What reality was not perceived (seen)?"

  "What communication was not acknowledged?"

This process IS NOT USED to handle SESSION ARC BREAKS but only to 
clean up auditing or the track. If the pc ARC breaks, don't use a 
process, find the missed charge.

Indeed, this process may be more valuable than at first believed, 
as one could put "In auditing ______" on the front of each one 
and straighten up sessions. And perhaps you could even run an 
engram with it. (The last has not been tested. "In auditing" + 
the three questions was wonderful on test. Two div TA in each 10 
mins on a very high TA case.)

"ARC Break Straightwire" of 1958 laid open implants like a band 
saw, which is what attracted my attention to it again. Many 
routine prefixes such as "In an organization" or "On engrams" or 
"On past lives" could be used to clear up past attitudes and 
overts.

We need some repetitive processes today. Cases too queasy to face 
the past, cases messed up by offbeat processes. Cases who have 
overts on auditing or Scientology or orgs. Cases pinned by 
session overts. The big mid ruds run inside an engram tend to 
make it go mushy. And Class I Auditors are without an effective 
repetitive process on modern technology. This is it.

A repetitive process, even though not looking for basic, implies 
that the process will be run until the charge is off and 
therefore creates no ARC breaks unless left unflat. Therefore, 
the process is safe if flattened.

                RUDIMENTS

Nothing is more detested by some pcs than rudiments on a session 
or GPM or RI. Why?

The same rule about ARC breaks applies.

The charge has been bypassed. How?

Consider the session is later than the incident (naturally). Ask 
for the suppress in the session. You miss the suppress in the 
incident (earlier by far). Result: Pc ARC breaks.

That's all there is to ARC breaks caused by session big mid ruds 
or mid ruds.

Example: "Scrambleable Eggs" won't RR. Auditor says, "On this 
item has anything been suppressed?" Pc eventually gets anxious or 
ARC breaks. Why? Suppress read. Yes, but where was the suppress? 
It was in the incident containing the RI, the pc looked for it in 
the session and thereby missed the suppress charge in the 
incident of the RI which, being bypassed charge unseen by pc and 
auditor, caused the ARC break. Remedy? Get the suppress in the 
incident, not the session. The RI RRs.

Also, the more ruds you use, the more you restimulate when doing 
Routine 3, because the suppress in the incident is not basic on 
Suppress, and if you clean just one clean, even to test, bang, 
there goes the charge being missed on Suppress and bang, bang, 
ARC break. Lightly, auditor, lightly.

           Q AND A ARC BREAKS

Q and A causes ARC breaks by BYPASSING CHARGE.

How? The pc says something. The auditor does not understand or 
acknowledge. Therefore, the pc's utterance becomes a bypassed 
charge generated by whatever he or she is trying to release. As 
the auditor ignores it and the pc reasserts it, the original 
utterance's charge is built up and up.

Finally, the pc will start issuing orders in a frantic effort to 
get rid of the missed charge. This is the source of pc orders to 
the auditor.

Understand and acknowledge the pc. Take the pc's data. Don't 
pester the pc for more data when the pc is offering data.

When the pc goes to where the auditor commands, don't say, "Are 
you there now?" as his going is thereby not acknowledged and the 
going built up charge. Always assume the pc obeyed until it's 
obvious the pc did not.

              ECHO METERING

The pc says, "You missed a suppress. It's ______" and the auditor 
reconsults the meter asking for a Suppress. That leaves the pc's 
offering an undischarged charge.

NEVER ASK THE METER AFTER A PC VOLUNTEERS A BUTTON.

Example: You've declared Suppress clean, pc gives you another 
suppress. Take it and don't ask Suppress again. That's Echo 
Metering.

If a pc puts his own ruds in, don't at once jump to the meter to 
put his ruds in. That makes all his offerings missed charge. Echo 
Metering is miserable auditing.

            MISSED WITHHOLDS

Needless to say, this matter of bypassed charge is the 
explanation for the violence of missed withholds.

The auditor is capable of finding out. So the pc's undisclosed 
overts react solely because the auditor doesn't ask for them.

This doesn't wipe out all technology about missed withholds. It 
explains why they exist and how they operate.

Indication is almost as good as disclosure. Have you ever had 
somebody calm down when you said "You've got missed withholds"? 
Well, it's crude but it has worked. Better is "Some auditor 
failed to locate some charge on your case." Or "We must have 
missed your goal." But only a meter assessment and a statement of 
what has been found would operate short of actually pulling the 
missed withholds.

          APPARENT BAD MORALE

There is one other factor on "Bad Morale" that should be 
remarked.

We know so much we often discard what we know in Scientology. But 
way back in Book One and several times after, notably 8-80, we 
had a Tone Scale up which the pc climbed as he was processed.

We meet up with this again running the Helatrobus Implants as a 
whole-track fact.

The pc rises in tone up to the lower levels of the Tone Scale. He 
or she comes up to degradation, up to apathy.

And it often feels horrible and, unlike an ARC break and the sad 
effect, is not cured except by more of the same processing.

People complain of their emotionlessness. Well, they come up a 
long ways before they even reach emotion.

Then suddenly they realize that they have come up to being able 
to feel bad. They even come up to feeling pain. And all that is a 
gain. They don't confuse this too much with ARC breaks but they 
blame processing. And then one day they realize that they can 
feel apathy!

And it's a win amongst wins. Before it was just wood.

And this has an important bearing on ARC breaks.

Everything on the whole Know to Mystery Scale that still lies 
above the pc finds the pc at effect. These are all on automatic.

Therefore, the pc in an ARC break is in the grip of the reaction 
which was in the incident, now fully on automatic.

The pc's anger in the incident is not even seen or felt by the 
pc. But the moment something slips, the pc is in the grip of that 
emotion as an automaticity and becomes furious or apathetic or 
whatever toward the auditor.

None is more amazed at himself or herself than the pc in the grip 
of the ARC break emotion. The pc is a helpless rag, being shaken 
furiously by the emotions he or she felt in the incident.

Therefore, never discipline or Q-and-A with an ARC broken pc. 
Don't join hands with his bank to punish him. Just find the 
bypassed charge and the automaticity will shut off at once to 
everyone's relief.

                ----------

Running Routine 3 is only unpleasant and unhappy to the degree 
that the auditor fails to quickly spot and announce bypassed 
charge. If he fails to understand this and recognize this, his 
pcs will ARC break as surely as a ball falls when dropped.

If an auditor has ARC breaky pcs, only one thing is basically 
wrong -- that auditor consistently misses charge or consistently 
fails to anticipate missed charge.

One doesn't always have to run the earliest. But one had better 
not ignore the consequences of not pointing it out. One doesn't 
have to discharge every erg from an RI always but one had better 
not hide the fact from the pc.

The adroit auditor is one who can spot earlier charge or 
anticipate ARC breaks by seeing where charge is getting missed 
and taking it up with the pc. That auditor's pcs have only the 
discomfort of the gradually rising tone and not the mess of ARC 
breaks.

It is possible to run almost wholly without ARC breaks and 
possible to stop them in seconds, all by following the rule: 
DON'T BYPASS CHARGE UNKNOWN TO THE PC.


L. RON HUBBARD
Founder

LRH:jw.rd.gm



******************************************************************

12. HCOB   19 Aug. 1963       How to Do an ARC Break Assessment


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

      HCO BULLETIN OF 19 AUGUST 1963

Central Orgs
Franchise


             SCIENTOLOGY TWO
         STAR-RATED HCO BULLETIN


    HOW TO DO AN ARC BREAK ASSESSMENT

   (HCO Secs: Check out on all technical
              executives and personnel. 
    Tech Dir: Check out on HCO Secs and
              Assoc/Org Secs.)


The successful handling of an ARC break assessment is a skilled 
activity which requires

1. Skill in handling a meter

2. Skill in handling the itsa line of the auditing cycle

3. Skill in assessment.

The lists given in HCO Bulletin of 5 July 63, ARC BREAK 
ASSESSMENTS, are used, either from that HCO Bulletin or amended.

There are several uses for ARC break assessments.

1. Cleaning up a session ARC break.

2. Cleaning up auditing in general.

3. Cleaning up a pc's or student's possible ARC breaks.

4. Cleaning up a member of the public's possible or actual ARC 
breaks.

5. Regular use on a weekly basis on staff or organization 
members.

There are others. Those above are the chief uses.

For long time periods the standard 18-button Prepcheck is faster, 
but an ARC break assessment is still useful in conjunction with 
it.

The drill is simple. If complicated by adding in R2H material, 
dating and other additives, the ARC break assessment ceases to 
work well and may even create more ARC breaks.

If used every time a pc gets in a little trouble in R3N or R3R, 
the ARC break assessment is being used improperly. In R2H, R3N, 
R3R sessions it is used only when the pc shows definite signs of 
an ARC break. To use it oftener constitutes no auditing.

Unnecessary use of an ARC break assessment may ARC break the pc 
with the assessment.

The ARC break assessment may be repaired by an 18-button 
Prepcheck "On ARC break assessments ________."


      ARC BREAK ASSESSMENT BY STEPS

STEP ONE:

Select the proper list. This is done by establishing what the pc 
has been audited on. If more than one type of bypassed charge is 
suspected, do more than one list. If the ARC break is not 
completely cured by one list, do another kind of list. (All lists 
have been in HCOBs as "L.")

STEP TWO:

Inform the pc that you are about to assess for any charge that 
might have been restimulated or bypassed on his or her case. Do 
not heavily stress the ARC break aspect. Right: "I am going to 
assess a list to see if any charge has been bypassed on your 
case." Wrong: "I'm going to try to cure (or assess) your ARC 
break."

STEP THREE:

Without regard to pc's natter, but with quick attention for any 
cognition the pc may have during assessment as to bypassed 
charge, assess the list.

Phrase the question in regard to the reason for the assessment -- 
"In this session" "During this week" "In Scientology" etc. Call 
each line once to see if it gives an instant read.

The moment a line gives a reaction, stop and do Step Four.

STEP FOUR:

When a line reacts on the needle, say to the pc, "The line 
________ reacts. What can you tell me about this?"

STEP FIVE:

Keep itsa line in. Do not cut the pc's line. Do not ask for more 
than pc has. Let pc flounder around until pc finds the charge 
asked for in Step Four or says there's no such charge. (If a line 
reacted because the pc did not understand it, or by Protest or 
Decide, make it right with the pc and continue assessing.)

STEP SIX:

In a session: If pc found the bypassed charge, ask pc, "How do 
you feel now?" If pc says he or she feels okay, cease assessing 
for ARC breaks and go back to session actions. If pc says there's 
no such charge or gets misemotional at auditor, keep on assessing 
on down the list for another active line, or even on to another 
list until the charge is found which makes pc relax.

In a routine ARC break check (not a session but for a longer 
period), don't stop assessing but keep on going as in Step Five, 
unless pc's cognition is huge.

              END OF STEPS

               ----------

Please notice: This is not R2H. There is no dating. The auditor 
does not further assist the pc with the meter in any way.

If the pc blows up in your face on being given a type of charge, 
keep going, as you have not yet found the charge. Typical 
response to wrong charge found: Pc: "Well, of course it's a cut 
communication! You've been cutting my communication the whole 
session. You ought to be retreaded... etc." Note here that pc's 
attention is still on auditor. Therefore, the correct charge has 
not been found. If the bypassed charge has been found, the pc 
will relax and look for it, attention on own case.

Several bypassed charges can exist and be found on one list. 
Therefore, in cleaning up a week or an intensive or a career (any 
long period) treat a list like rudiments, cleaning everything 
that reacts.

Blowdown of the tone arm is the meter reaction of having found 
the correct bypassed charge. Keep doing Steps One to Six until 
you get a blowdown of the tone arm. The pc feeling better and 
being happy about the ARC break will coincide almost always with 
a tone arm blowdown.

You can, however, undo a session ARC break assessment by 
continuing beyond the pc's cognition of what it is. Continuing an 
assessment after the pc has cognited invalidates the pc's 
cognition and cuts the itsa line and may cause a new ARC break.

Rarely, but sometimes, the ARC break is handled with no TA 
blowdown.

                ----------
  
          PURPOSE OF ASSESSMENT

The purpose of an ARC break assessment is to return the pc into 
session or into Scientology or into an org or course. Bypassed 
charge can cause the person to blow out of session, or out of an 
org or a course or Scientology.

WITH A SESSION (formerly "In"): Is defined as "INTERESTED IN OWN 
CASE AND WILLING TO TALK TO THE AUDITOR." AGAINST SESSION: 
Against session is defined as "ATTENTION OFF OWN CASE AND TALKING 
AT THE AUDITOR IN PROTEST OF AUDITOR, PT AUDITING, ENVIRONMENT OR 
SCIENTOLOGY."

WITH SCIENTOLOGY: With Scientology is defined as "INTERESTED IN 
SUBJECT AND GETTING IT USED." AGAINST SCIENTOLOGY: Against 
Scientology is defined as "ATTENTION OFF SCIENTOLOGY AND 
PROTESTING SCIENTOLOGY BEHAVIOR OR CONNECTIONS."

WITH ORGANIZATION: With organization can be defined as 
"INTERESTED IN ORG OR POST AND WILLING TO COMMUNICATE WITH OR 
ABOUT ORG." AGAINST ORGANIZATION: Against organizationness is 
defined as "AGAINST ORGANIZATION OR POSTS AND PROTESTING AT ORG 
BEHAVIOR OR EXISTENCE."

The data about ARC breaks can be expanded to marriage, companies, 
jobs, etc. Indeed to all dynamics -- With Dynamic, Against 
Dynamic.

What it boils down to is this: There are only two conditions of 
living, but many shades of gray to each one.

These conditions are

1. LIFE: NOT ARC BROKEN: Capable of some affinity for, some 
reality about and some communication with the environment; and

2. DEATH: ARC BROKEN: Incapable of affinity for, reality about 
and communication with the environment.

Under (1) we have those who can disenturbulate themselves and 
make some progress in life.

Under (2) we have those who are in such protest that they are 
stopped and can make little or no progress in life.

(1) we consider to be in some ARC with existence.

(2) we consider to be broken in ARC with existence.

In a session or handling the living lightning we handle, people 
can be hit by a forceful charge of which they are only minutely 
aware but which swamps them. Their affinity, reality and 
communication (life force) is retarded or cut by this hidden 
charge and they react with what we call an ARC break or have an 
ARC broken aspect.

If they know what charge it is, they do not ARC break or they 
cease to be ARC broken.

It is the unknown character of the charge that causes it to have 
such a violent effect on the person.

People do not ARC break on known charge. It is always the hidden 
or the earlier charge that causes the ARC break.

This makes life look different (and more understandable). People 
continuously explain so glibly why they are acting as badly as 
they are. Whereas, if they really knew, they would not act that 
way. When the true character of the charge (or many charges as in 
a full case) is known to the person, the ARC break ceases.

How much bypassed charge does it take to make a case? The whole 
sum of past bypassed charge.

This fortunately for the pc is not all of it in constant 
restimulation. Therefore, the person stays somewhat in one piece 
but prey to any restimulation.

Auditing selectively restimulates, locates the charge and 
discharges it (as seen on the action of a moving tone arm).

However, accidental rekindlings of past charge unseen by pc or 
auditor occur and the pc "mysteriously" ARC breaks.

Similarly, people in life get restimulated also, but with nobody 
to locate the charge. Thus, Scientologists are lucky.

In heavily restimulated circumstances the person goes OUT OF. In 
such a condition people want to stop things, cease to act, halt 
life, and failing this they try to run away.

As soon as the actual bypassed charge is found and recognized as 
the charge by the person, up goes affinity and reality and 
communication and life can be lived.

Therefore, ARC breaks are definite, their symptoms are known, 
their cure is very easy with this understanding and technology.

An ARC break assessment seeks to locate the charge that served, 
being hidden, as a whip-hand force on the person. When it is 
located, life returns. Locating the actual bypassed charge is 
returning life to the person.

Therefore, properly handling ARC breaks can be called, with no 
exaggeration "Returning life to the person."

One further word of caution: As experience will quickly tell you, 
seeking to do anything at all with an earlier bypassed charge 
incident which led to the ARC break, immediately the earlier 
incident is found will lead to a vast mess.

Let the pc talk about it all the pc pleases. But don't otherwise 
try to run it, date it or seek to find what bypassed charge 
caused the earlier incident. In assessing for ARC breaks, keep 
the itsa line in very well and keep the whatsit out in every 
respect except as contained in the above Six Steps.

                ----------

                 SUMMARY

An ARC break assessment is simple stuff, so simple people are 
almost certain to complicate it. It only works when kept simple.

Old auditors will see a similarity in an ARC Break Assessment 
List and old end rudiments. They can be handled much the same but 
only when one is covering a long time period. Otherwise assess 
only to cognition and drop it.

The trouble in ARC break assessments comes from additives by the 
auditor, failure to keep on with additional lists if the type of 
charge causing the ARC break isn't found on the first list 
chosen, failure to read the meter and failure to keep the itsa 
line in.

Doing ARC break assessments to cure ARC breaks is not the same 
drill as R2H and confusing the two leads to trouble.

Handled skillfully as above, ARC break assessing cures the great 
majority of the woes of auditing, registraring, training and 
handling organization. If you find you aren't making ARC break 
assessments work for you, check yourself out on this HCO Bulletin 
carefully, review your meter reading and examine your handling of 
the itsa line. If you want live people around you, learn to 
handle ARC break assessments.

Don't worry about pcs getting ARC breaks. Worry about being able 
to cure them with assessment until you have confidence you can. 
There's nothing so uplifting as that confidence, except perhaps 
the ability to make any case get TA motion.

Don't ever be "reasonable" about an ARC break and think the pc is 
perfectly right to be having one "because..." If that ARC break 
exists, the pc doesn't know what's causing it and neither do you 
until you and the pc find it! If you and the pc knew what was 
causing it, there would be no further ARC break.


L. RON HUBBARD
Founder

LRH:dr.cden.gm



******************************************************************

13. HCOB    7 Sept 1964 II    PTPS, Overts and ARC Breaks


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

     HCO BULLETIN OF 7 SEPTEMBER 1964
                 Issue II

Remimeo
Franchise
Sthil Students

                ALL LEVELS

        PTPs, OVERTS AND ARC BREAKS


Just to remind you, other auditing is not possible in the 
presence of present time problems and overts. No auditing is 
possible in the presence of an ARC break.

These are data like "Acknowledge the pc," "An auditor is one who 
listens," etc. These belong in the ABCs of Scientology.

          PRESENT TIME PROBLEMS

When a pc has a PTP and you don't handle it, you get no gain. 
There will be no rise on a personality test graph. There will be 
little if any TA action. There will be no gain in the session. 
The pc will not make his session goals. Etc. Etc. So you don't 
audit pcs who have PTPs on anything but the PTPs the pc has.

And you don't audit PTPs slowly and forever. There are numerous 
ways of handling PTPs. One of them is "What communication have 
you left incomplete about that problem?" A few answers and poof! 
no PTP. Another is "What doesn't (that person or thing pc is 
having PTP with) know about you?" Other versions of overts and 
withholds can be used. These are all fast PTP handling methods 
and they get rid of the PTP and you can audit what you started to 
audit.

The mark of a ruddy amateur in auditing is somebody who can 
always do successful assists but can't do a real session. The 
secret is, in an assist you are handling the PTP, aren't you? So 
you never audit over the top of (in the presence of) a PTP!

Another circumstance is "can't get down to real auditing because 
the pc always has so many PTPs." This is only a confession that 
one can't handle a PTP and then get on with the session. One 
fumbles with the PTPs so badly as an auditor one never really 
handles the pc's PTPs, so of course one never gets on with the 
job at hand-auditing the pc.

The pro, in a real session, just handles the PTPs quickly, gets 
the pc into session and gets on with whatever should be run.

                 OVERTS

Overts are the other principal source of getting no gain.

Here we really can tell the goony birds from the eagles 
professionally.

No pro would think of auditing a pc on other processes in the 
presence of overts.

1. The pro would recognize by the pc's natter or lack of previous 
gain that the pc had overts;

2. The pro would know that if he tried to do something else 
besides pull these overts, the pc would eventually get critical 
of the auditor; and

3. The pro wouldn't (a) fail to pull the real overts or (b) ARC 
break the pc in getting the overts off.

If one gets "reasonable" about the pc's condition and starts 
agreeing with the motivators ("look at all the bad things they 
did to me"), thus ignoring the overts, that's the end of gains 
for that pc with that auditor.

If one is clumsy in recognizing overts, if one fails to get the 
pc to give them up, if one fails to properly acknowledge the 
overt when given, or if one demands overts that aren't there, 
overt pulling becomes a howling mess.

Because, then, getting the pc overts off is a tricky business, 
auditors sometimes become shy of doing it. And fall as auditors.

Sometimes pcs who have big overts become highly critical of the 
auditor and get in a lot of snide comments about the auditor. If 
the overt causing it is not pulled, the pc will get no gains and 
may even get ARC broken. If the auditor doesn't realize that such 
natter always indicates a real overt, when pcs do it, eventually 
over the years it makes an auditor shy of auditing.

Auditors buy "critical thoughts" the pc "has had" as real overts, 
whereas a critical thought is a symptom of an overt, not the 
overt itself. Under these critical thoughts a real overt lies 
undetected.

Also, I love these pcs who "have to get off a withhold about you. 
Last night Jim said you were awful..." An experienced auditor 
closes the right eye slightly, cocks his head a bit to the left 
and says, "What have you been doing to me I haven't known about?" 
"I thought..." begins the pc. "The question is," says the old 
pro, "'What have you been doing to me that I don't know about? 
The word is DOING."' And off comes the overt like "I've been 
getting audited by Bessy Squirrel between sessions in the coffee 
shop."

Well, some auditors are so "reasonable" they never really learn 
the mechanism and go on getting criticized and getting no gains 
on pcs and all that. I once heard an auditor say, "Of course he 
was critical of me. What he said was true. I'd been doing a 
terrible job." The moral of this story is contained in the fact 
that this auditor's pc died. A rare thing but a true one. The pc 
had terrible overts on Scientology and the auditor, yet this 
auditor was so "reasonable" those overts were never cleaned up. 
And that was the end of those auditing sessions.

It's almost never that drastic, but if an auditor won't pull 
overts, well, auditing gets pretty unpleasant and pretty 
pointless, too.

A lack of grasp of the overt-motivator sequence (when somebody 
has committed an overt, he or she has to claim the existence of 
motivators -- the Ded-Dedex version of Dianetics -- or simply
when one has a motivator, he is liable to hang himself by
committing an overt) puts an auditor at a very bad disadvantage.
Howling pcs and no pc wins.

               ARC BREAKS

You can't audit an ARC break. In fact, you must never audit in 
the presence of one.

Auditing below Level III, the best thing to do is find an auditor 
who can do ARC break assessments.

At Level III and above, do an ARC break assessment on the pc. An 
ARC break assessment consists of reading an ARC break list 
appropriate to the activity to the pc on a meter and doing 
nothing but locate and then indicate the charges found by telling 
the pc what registered on the needle.

That isn't auditing because it doesn't use the auditing comm 
cycle. You don't ack what the pc says, you don't ask the pc what 
it is. You don't comm. You assess the list between you and the 
meter, same as no pc there. Then you find what reads and you tell 
the pc. And that's all.

A bypassed charge assessment is auditing because you clean every 
tick of the needle on the list being assessed. The pc is acked, 
the pc is permitted to itsa and give his opinions. But you never 
do a bypassed charge assessment on an ARC broken pc. You do an 
ARC break assessment as per the paragraph above this one.

These two different activities unfortunately have the word 
"assessment" in common and they use the same list. Therefore, 
some students confuse them. To do so is sudden death.

You can really clobber a pc by doing a bypassed charge assessment 
on an ARC broken pc. And also you can ARC break a pc by doing an 
ARC break assessment on a pc who isn't (or has ceased to be) ARC 
broken.

So unless you have these two separate and different actions --
the ARC break assessment and the bypassed charge assessment -- 
clearly understood and can do both of them well and never get too 
rattled to know which one to use, you can get into plenty of
trouble as an auditor.

Only auditing over the top of an ARC break can reduce a graph, 
hang the pc up in sessions or worsen his case. So it's the next 
to the most serious blunder that an auditor can make. (The most 
serious error is to deny assistance either by not trying to get 
the pc into session or not using Scientology at all.)

Auditing an ARC broken pc and never realizing it can lead to very 
serious trouble for the auditor and will worsen the pc's case --
the only thing that will.

                 SUMMARY

It is elementary auditing knowledge that no gains occur in the 
presence of PTPs or overts and that cases worsen when audited 
over the top of an ARC break.

There aren't "lots more conditions that can exist." Given an 
auditing session, there are only these three barriers to auditing 
gain.

When you do clay table auditing or any other kind of auditing, 
the rules all still apply. A change of process or routine doesn't 
change the rules.

In doing clay table auditing off a meter, one still handles the 
elements of a session. One puts the pc on the meter to start off 
and checks for PTPs, overts, withholds, even ARC breaks, handles 
them quickly and then goes into the body of the session. Much the 
same as the oldest Model Session rudiments. One doesn't use mid 
ruds or buttons to get started. One just knows the things that 
mustn't be there (PTPs, overts, ARC breaks) and checks for them, 
handles if found and goes on with the main session activity. If a 
PTP or an overt or an ARC break shows up, one handles them, 
putting the pc back on the meter if necessary. When they are 
handled, the pc is put back into the main activity of the 
session.

It's true of any auditing that gets done. It isn't likely to 
alter and actually no new data is likely to be found that 
controverts any of this. The phenomena will still be the same 
phenomena as long as there are pcs. Ways of handling may change 
but not these basic principles.

They're with the auditor in every session ever to be run. So one 
might as well stay alert to them and be continuously expert in 
handling them.

They are the only big reefs on which an auditing session can go 
up high and dry, so their existence, causes and cures are of the 
greatest possible importance to the skilled auditor.


L. RON HUBBARD
Founder

LRH:jw.cden.gm



******************************************************************

14. HCOB   29 Mar. 1965       ARC Breaks


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

      HCO BULLETIN OF 29 MARCH 1965

Remimeo
Franchise
Students

               ALL LEVELS

               ARC BREAKS


Great news!

I've found the basis of ARC breaks!

As you know, only a PTP (present time problem) can hold a graph 
unchanging and only an ARC break can lower one. Therefore, the 
anatomy of an ARC break is more vital to know, as it can worsen, 
than the anatomy of a PTP. But both are very important and with 
the overt act and misunderstood words in study form the vital 
four things anyone should know in auditing pcs.

The average student has a hard time getting rid of ARC breaks in 
others, mostly because he never really finds the ARC break. One 
auditor was sure a pc had been ARC broken by "the last few inches 
of a lecture tape" and was madly calling Washington to borrow the 
tape so the poor pc could "listen to it again to cure his ARC 
break"! Well, I don't mind being cause, but my tape never ARC 
broke the pc. The auditor just didn't locate the charge.

The whole trick is to keep cleaning up the ARC break until the pc 
is happy again and then quit. When you find it, that's it. You 
don't find it and still have an ARC broken pc! No, the terribly 
simple truth is that

1. The pc is ARC broken because something happened.

2. The pc will continue to be ARC broken until the thing is 
found.

3. The ARC break will vanish magically when the source is found.

Finding the ARC break and indicating it clears the ARC break. If 
it doesn't clear on what you find, then you haven't found it!

You must not continue to run a pc on some process when the pc is 
ARC broken. You must find the ARC break and clear it.

The pc will go into a sad effect if you don't find the ARC break 
but, instead, continue the process. If you think you have found 
the ARC break (and haven't) and then go on auditing, the pc will 
go into a sad effect.

ARC broken pcs are easy to identify. They gloom and misemote. 
They criticize and snarl. Sometimes they scream. They blow. They 
refuse auditing.

If you can read a lighted neon sign at 10 feet on a dark night, 
you can detect a pc who has an ARC break. Some auditors can 
detect them sooner than others. I can see one coming in a pc
1 1/2 hours of auditing before the pc starts to get misemotional
in earnest. Some newcomer in the business might not detect one
until the pc wraps a chair around the auditor's head. As I say,
the ability to perceive one varies. The better you are the sooner
you see one. If an auditor's pc isn't bright and happy, there's
an ARC break there with life or the bank or the session.

The thing to do is find it and clean it up.

And now all is revealed. This is what makes an ARC break occur:

AN ARC BREAK OCCURS ON A GENERALITY OR A NOT THERE.

             THE GENERALITY

Example of a generality:

"They say you are cold-hearted." "Everybody thinks you are too 
young." "The People Versus Sam Jones." "The will of the masses."

           CASE MANIFESTATION

Example: Little boy screaming in rage when he makes a mistake in 
drawing. Auditor observes little boy is upset.

Auditor: "What are you upset about?"
Little Boy: (howling) "My drawing is no good!"
Auditor: "Who said your drawing is no good?"
Little Boy: (crying) "The teachers at school (plural)."
Auditor: "What teacher (singular)?"
Little Boy: (sobbing) "Not the teachers, the other children 
(plural)!"
Auditor: "Which one of the other children?"
Little Boy: (suddenly quiet) "Sammy."
Auditor: "How do you feel now?"
Little Boy: (cheerfully) "Can I have some ice cream?"

               THE FORMULA

1. Ask what the pc is upset about.

2. Ask who thought so.

3. Repeat the generality the pc used and

4. Ask for the singular.

5. Keep (3) and (4) going until the pc is happy.

As it's a near Q and A, it should be awfully easy. They name 
prunes, you say what prune is prunes.

                  RESULT

It's quite magical done barehanded or on a meter.

                  ERRORS

You can miss in English sometimes on YOU. The pc says YOU are 
mean. We have no plural or singular signal in the word YOU. 
Therefore, a statement that "YOU are ARC breaking me" or "YOU ARE 
MEAN" may not mean, as an egocentric auditor may take it, the 
auditor, but YOU may be being used as THE WHOLE WORLD. The above 
formula holds (1) to (5). Just find out "Which person is meant by 
the word YOU?"

Our old "Look at me, who am I" was not too wrong.

So next time your pc says, "The Instructors are mean," don't be 
goofy enough to indicate the charge with "OK, you are ARC broken 
because the Instructors are mean." And then be amazed when the 
ARC break continues. You didn't find out "What Instructor is 
Instructors?" If you ask a bit further, you'll find it probably 
wasn't "the Instructors" but somebody else. And that somebody 
will be a unit, not a group.

A less workable but interesting approach is "Who uses the word 
'everybody' frequently?" It's of interest only because 
"everybody" makes a dispersal which the pc can't see through. It 
will take quite a while sometimes for a pc to spot such a person!

How many people have died heartbroken because "they" were mean to 
him. And it was just one vicious being who had been blown up to 
"they."

              THE NOT THERE

The not there is also a generality because it can be anywhere. 
But it is a special case.

When something becomes unlocatable, it can cause an ARC break.

The cure for this one is to find out what's gone.

If you see somebody with a cold, ask "Who's gone?" and you'll be 
amazed at the recovery if you pursue the matter.

One concludes it's less the loss than not knowing where something 
has gotten to, making a one into a generality.

The common response to sudden loss is to feel everything is gone 
or going.

This is the state of anxiety explained.

The beaten and downtrodden respond well on this (when brought up 
through normal levels to the Level of Remedies).

A very sneaky question is "Who (or what) was everything to you?"

But use it sparingly. The pc will go whole track like a flash if 
overworked.

Remarkably (at this late date to find it!) that's why he rather 
fancies his pictures! At least he has a picture of it!

Dreams follow a sudden loss. It's an effort to orient oneself and 
get something back.

           LEVEL VI ARC BREAKS

Of course, there's nothing wrong really with a thetan but his 
reactive bank. He can recover from the rest. And his reactive 
bank is full of generalities, which explains the hard ARC breaks 
of Level VI. But don't tamper with Level VI if the pc belongs at 
II. You can get enough locks off any day from normal life to cure 
the ARC breaks you'll encounter getting up to VI.

Main thing to know is, AN ARC BREAK OCCURS BECAUSE OF A 
GENERALITY OR A NOT THERE.

Fortunately, it doesn't always occur. Only sometimes.

And when it does:

Find the singular form of the generality.

In admin particularly you save more executives that way. And in 
auditing you just don't have failed cases or blows if you know 
it.


L. RON HUBBARD
Founder

LRH:wmc.aj.cden.gm



******************************************************************

15. HCOB    4 Apr. 1965       ARC Breaks and Missed Withholds


      HUBBARD COMMUNICATIONS OFFICE
Saint Hill Manor, East Grinstead, Sussex

      HCO BULLETIN OF 4 APRIL 1965

Remimeo
Franchise


    ARC BREAKS AND MISSED WITHHOLDS


The primary error one can make in ARC break handling is to handle 
the pc with ARC break procedure when the pc really has a missed 
withhold.

As some auditors dislike pulling withholds (because they run into 
pcs who use it to carve the auditor up, such as "I have a 
withhold that everybody thinks you are awful ----"), it is easier 
to confront the idea that a pc has an ARC break than the idea 
that the pc has a withhold.

In case of doubt one meter checks on a withhold to see if it is 
nonexistent ("Am I demanding a withhold you haven't got?"). If 
this is the case, the TA will blow down. If it isn't the case, 
the needle and TA remain unchanged. If the pc's nattery or ARC 
breaky condition continues despite finding bypassed charge, then 
of course it is obviously a withhold.

ARC break finding does work. When the pc doesn't change despite 
skillful ARC break handling, locating and indicating, it was a 
withhold in the first place.

The hardest pc to handle is the missed withhold pc. They ARC 
break but you can't get the pc out of it. The answer is, the pc 
had a withhold all the time that is at the bottom of all these 
ARC breaks.

Scientology auditing does not leave the pc in poor condition 
unless one goofs on ARC breaks.

ARC breaks occur most frequently on people with missed withholds.

Therefore, if a pc can't be patched up easily or won't stay 
patched up on ARC breaks, there must be basic withholds on the 
case. One then works hard on withholds with any and all the tools 
that we've got.

ARC breaks don't cause blows. Missed withholds do. When you won't 
hear what the pc is saying, then you have made him have a 
withhold and it responds as a missed withhold.

In short, the bottom of ARC breaks is a missed withhold.

But an antisocial act done and then withheld sets the pc up to 
become "an ARC breaky pc." It isn't an accurate remark really 
since one has a pc with withholds who on being audited ARC breaks 
easily. So the accurate statement is "the pc is a withholdy-type 
pc that ARC breaks a lot." Now, that type exists. And they sure 
have lots of subsequent ARC breaks and are regularly being 
patched up.

If you have a pc, then, who seems to have a lot of ARC breaks, 
the pc is a "withholdy pc" not an "ARC breaky pc." Any auditor 
miss causes a pc blow-up. The auditor by calling this pc an "ARC 
breaky pc" is not using a description which leads to a resolution 
of the case as thousands of ARC break assessments leave the case 
still liable to ARC break. If you call such a case that ARC 
breaks a lot a "withholdy pc that ARC breaks a lot," then you can 
solve the case. For all you have to do is work on withholds.

The actual way to handle a "withholdy pc that ARC breaks a lot" 
after you've cooled off the last of his many ARC breaks is:

1. Get the pc to look at what's going on with his sessions.

2. Get the pc in comm.

3. Get the pc to look at what's really bugging him.

4. Get the pc's willingness to give withholds up on a gradient.

5. Bring the pc to an understanding of what he's doing.

6. Get the pc's purpose in being audited in plain view to him or 
her.

Those are, of course, the names of the first six grades. However, 
low down, these six things are all crushed together and you could 
really pursue that cycle in one session just to get the pc up a 
bit without even touching the next grade up.

Whenever I see a sour-faced person who has been "trained" or is 
being "trained," I know one thing -- there goes a pc with lots of 
withholds. I also know, there is a pc who ARC breaks a lot in 
session. And I also know his co-auditor is weak and flabby as an 
auditor. And I also know his auditing supervisor doesn't shove 
the student auditor into doing the process correctly.

One sour-faced student, one glance and I know all the above 
things, bang!

So why can't somebody else notice it?

Auditing is a pleasure. But not when an auditor can't tell a 
withhold from an ARC break and doesn't know that continual ARC 
breaks are caused by missed withholds on the bottom of the chain.

I never miss on this. Why should you?

The only case that will really "bug you" is the CONTINUOUS OVERT 
case. Here's one that commits antisocial acts daily during 
auditing. He's a nut. He'll never get better, case always hangs 
up.

Unless you treat his continual overts as a solution to a PTP. And 
find what PTP he's trying to solve with these crazy overt acts.

You see, we can even solve that case.

BUT, don't go believing Scientology doesn't work when it meets an 
unchanging or continually misemotional pc. Both of these people 
are foul balls who are loaded with withholds.

We've cracked them for years and years now.

But not by playing patty-cake or "slap my wrist."

Takes an auditor, not a ladyfinger.

"Mister, you've been wasting my time for three sessions. You have 
withholds. Give!" "Mister, you refuse just once more to answer my 
question and you're for it. I've checked this meter. It's not a 
withhold of nothing. You have withholds. Give!" "Mister, that's 
it. I am asking the D of P to ask the Tech Sec for a Comm Ev on 
you from HCO for no report."

If skill couldn't do it, demand may. If demand couldn't do it, a 
Comm Ev sure will.

For it's a no report!

How can you make a man well when he's got a sewer full of slimy 
acts.

Show me any person who is critical of us and I'll show you crimes 
and intended crimes that would stand a magistrate's hair on end.

Why not try it? Don't buy "I once stole a paper clip from the 
HASI" as an overt or "You're a lousy auditor" as a withhold. 
Hell, man, people who tell you those things just stole your lunch 
or intend to empty the till.

Get clever, auditor. Thetans are basically good. Them that 
Scientology doesn't change are good -- but down underneath a pile 
of crimes you couldn't get into a confession story magazine.

Okay. Please don't go on making this error. It grieves me.


L. RON HUBBARD
Founder

LRH:ml.rd.gm





